Expose iova management and dma_map api in vfio mem utils to users#124
Closed
Wangl56 wants to merge 1 commit intointel:mainfrom
Closed
Expose iova management and dma_map api in vfio mem utils to users#124Wangl56 wants to merge 1 commit intointel:mainfrom
Wangl56 wants to merge 1 commit intointel:mainfrom
Conversation
This change is to expose the below APIs to user to let users be able to leverage them to map the user allocated memory to iova address and configure it to qat dma engine to avoid none-necessary memory copy when qat engine transfer data to user memory. iova_release -> qae_iova_release allocate_iova -> qae_allocate_iova dma_map_slab -> qae_dma_map_slab dma_unmap_slab -> qae_dma_unmap_slab
Contributor
Contributor
|
Closing. Superseded by #124. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change is to expose the below APIs to user to let users be able to leverage them to map the user allocated memory to iova address and configure it to qat dma engine to avoid none-necessary memory copy when qat engine transfer data to user memory.
iova_release -> qae_iova_release
allocate_iova -> qae_allocate_iova
dma_map_slab -> qae_dma_map_slab
dma_unmap_slab -> qae_dma_unmap_slab